5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
- Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-4: Files and Fields

Files Record Protection Option


The Record Protection overlay, shown below, displays when you select the record protection option from the Files/Fields screen. The features in this overlay allow you to prevent users from accessing, modifying or deleting records or record keys.

Files Record Protection Overlay

 

These fields appear on the Record Protection Overlay:

The Delete Protection field allows you to designate a logic or numeric field for record delete protection. A logic field with a value of 'yes' , or a numeric field with a non-zero value, signals to APPX to prevent the record it belongs to from being deleted during data entry. The same field can be designated as both Delete Protection and Key Protection. Protection is only provided within an input process during Live Operations (see Operational Phase). This field can be used to prevent the creation of orphan records by prohibiting the deletion of records referenced by other records anywhere in a database. You must explicitly maintain the value in this field.

The Key Protection field allows you to designate a logic or numeric field for record key protection. A logic field with a value of 'yes' , or a numeric field with a non-zero value, signals to APPX to prevent the primary key for that record from being changed during data entry. The same field can be designated as both Delete Protection and Key Protection.. Protection is only provided within an input process during Live Operations (see Operational Phase). This field can be used to maintain the integrity of a database by prohibiting the modification of keys referenced by other records anywhere in the database. You must explicitly maintain the value in this field.

The Record Access field allows you to designate a four-character alphanumeric field for security code. All record accesses upon this file within APPX processes check the contents of this field for access class. If the user does not have rights to the security code stored in this field for the desired record, APPX responds as if the record is not on file. The value in this field must be maintained by the designer and must be four numeric characters. If blank, there are no restrictions.

Application Design Manual                                         "Powered by Appx Software"

1009

©2006 By APPX Software, Inc. All Rights Reserved